build(deps): bump @browserbasehq/sdk from 2.6.0 to 2.16.0 - #36
build(deps): bump @browserbasehq/sdk from 2.6.0 to 2.16.0#36dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@browserbasehq/sdk](https://github.com/browserbase/sdk-node) from 2.6.0 to 2.16.0. - [Release notes](https://github.com/browserbase/sdk-node/releases) - [Changelog](https://github.com/browserbase/sdk-node/blob/main/CHANGELOG.md) - [Commits](browserbase/sdk-node@v2.6.0...v2.16.0) --- updated-dependencies: - dependency-name: "@browserbasehq/sdk" dependency-version: 2.16.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
|
PR author is not in the allowed authors list. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Deliberately left out of the batched update in #46, which covered the other ten pending bumps. Between 2.6.0 and the current 2.x releases this SDK changed its default HTTP transport. It previously used node-fetch with a keep alive agent; it now calls the platform The effect is that Browserbase's reported latency would improve by roughly one handshake round trip per run, without anything changing on the provider side, which also shifts its position relative to the other providers. That makes it a question about benchmark methodology rather than a routine dependency update, so it seemed better to raise it than to fold it into a bulk bump. Two reasonable ways forward, whichever fits the project's intent:
Either is fine, but it is worth being an explicit choice. |
1 participant
Bumps @browserbasehq/sdk from 2.6.0 to 2.16.0.
Release notes
Sourced from @browserbasehq/sdk's releases.
... (truncated)
Changelog
Sourced from @browserbasehq/sdk's changelog.
... (truncated)
Commits
525603drelease: 2.16.0 (#194)06d58fcrelease: 2.15.0 (#190)1d46d4erelease 2.14.1 (#192)39b340dWorkaround premature-close issue in 24.17.0 (#191)5804781release: 2.14.0 (#188)656a0ccrelease: 2.13.0 (#187)6d1cb26release: 2.12.0 (#186)316fc93release: 2.11.0 (#182)6ff98d3release: 2.10.0 (#181)a4956b1release: 2.9.0 (#179)You can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)